Bundled application for load management system

ABSTRACT

Load management systems and methods are described. A load management system comprises a database storing load information, a mobile application associated with a user account and executable on a mobile device. The mobile application includes a main application and independently executable sub-applications corresponding to workflow progresses in the distribution center. The mobile application when executed, accesses the sub-applications in response to a user logging in to the main mobile application. The sub-applications inherit credentials from the main application and communicate with each other in response to inheriting the credentials.

RELATED APPLICATION

This application claims the benefit of, and priority to, U.S.Provisional Patent Application No. 62/677,822, filed May 30, 2018, thecontent of which is incorporated herein by reference in its entirety.

BACKGROUND

In a distribution center, a truck driver needs to supply paperwork tothe distribution center before dropping off the freight they are moving.These processes, for example, gate-in, gate-out, proof of delivery,etc., can be time consuming and inaccurate.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are not intended to be drawn to scale. In thedrawings, each identical or nearly identical component that isillustrated in various figures may be represented by a like numeral. Forpurposes of clarity, not every component may be labeled in everydrawing. In the drawings:

FIG. 1 is a block diagram showing a load management system according tovarious embodiments of the present disclosure.

FIGS. 2A-2D are flow diagrams illustrating a load managing processperformed by the load management system in a distribution centeraccording to various embodiments of the present disclosure.

FIGS. 3A-3D are graphical user interfaces (GUIs) of a mobile applicationof the load management system according to an exemplary embodiment ofthe present disclosure.

FIGS. 4A-4D are graphical user interfaces (GUIs) of a gate-insub-application of a mobile application of the load management systemaccording to an exemplary embodiment of the present disclosure.

FIG. 5 is a block diagram of an exemplary computational device withvarious components which can be used to implement various embodiments.

FIG. 6 is block diagram of an exemplary distributed system suitable foruse in exemplary embodiments.

DETAILED DESCRIPTION

Described in detail herein is a load management system including anapplication management system for a distribution center. Loadinformation related to loads destined for the distribution center can bestored in a database. The load information can include an identificationassociated with each of the loads. The system can include a mobileapplication associated with a user account and the mobile applicationcan executable on a mobile device to implementation the applicationmanagement system. The mobile application can include a main applicationand independently executable sub-applications corresponding to workflowprogresses in the distribution center. The mobile device executes themobile application to access the sub-applications in response to a userlogging in to the main mobile application associated with thecorresponding user account. Each of the main application and thesub-applications can be separate and distinct executables and can beexecuted as separate and distinct instances. In response to execution ofthe main application, the mobile device renders, on a display of themobile device and within a graphical user interface of the mainapplication, selectable icons corresponding to the sub-applications onthe mobile device. The sub-applications can inherit credentials from themain application and communicate with each other in response toinheriting the credentials.

The mobile device can activate a first sub-application in response tothe user selecting a first one of the selectable icons corresponding tothe first sub-application. In response to execution of the firstsub-application, the mobile device can acquire at least one of theidentifications of the loads, query the database with the acquired atleast one of the identifications of the loads for the load informationrelated to a specified load, receive the queried load information fromthe database, update the load information based on information of loaddocumentation, and generate a machine-readable representationcorresponding to the at least one of the identifications of the load.

The mobile device can activate a second sub-application in response tothe user selecting a second one of the selectable icons corresponding tothe second sub-application. In response to execution of the secondsub-application, the mobile device can acquire the machine-readablerepresentation generated by the first sub-application, query thedatabase, with the machine-readable representation, for the loadinformation related to the load, receive the queried load informationfrom the database, acquire pallet information, and update the loadinformation based on the pallet information.

The mobile application can be programmed to handle driver processes atthe distribution center to automate and streamline driver interactionsat the distribution center. The mobile application can be a bundle forindividual and distinct driver tools and can provide a platform tomodify and standardize workflow. As described herein, the mobileapplication houses a number of sub-applications which the driver may useas he/she enters the distribution center, loads or unloads cargo andfinally departs from the distribution center. The mobile application canallow a user to register using a federated login, for example, fromYahoo, Vudu, Facebook, etc. The mobile application can be downloaded andinstalled on the mobile device as a bundle including the mainapplication and the sub-applications.

The load management system can be used with a scheduler database, usermobile devices, and other distribution center systems to facilitate anexpedited and accurate check-in process for trailer drivers and thefreight on the trailers, and to direct autonomous yard vehicles. Theload management system can receive load information generated by thescheduler and compile the information such that the load information canbe shared electronically when the driver arrives at the distributioncenter. The driver also has the option of inputting selected informationinto the mobile app when the driver is between the freight pickuplocation and the DC, which can eliminate the need for an assetprotection (AP) associate at the distribution center to manually enterthe information into a yard management system, and eliminate paperworkfrom the processes in the distribution center to reduce theinteractiontime at the truck gate of the distribution center and toreduce the potential for human error. The load information can be sentto the yard management system (YMS) and YMS can send instructioninformation to the driver regarding where to load or unload the freightin the distribution center.

Accordingly, systems and methods provided herein can make the processesin a distribution center, such as gate-in, proof-of delivery, gate-out,etc., faster and with higher accuracy as a driver can be guided to thecorrect location by the mobile application once the driver enters theyard area of a distribution center.

Referring now to FIG. 1, an exemplary load management system 100includes a computing system 110, user device(s) 119, and data storagesdevice(s) 140. The computing system 110 includes memory 104, a processor105 and communication interface 107. In some embodiments, the computingsystem 110 is configured to execute a processing module 109 and alsoincludes, or is able to access, an autonomous yard vehicle database 111and a user account database 112.

The autonomous yard vehicle database 111 can include informationassociated with the autonomous yard vehicles in the distribution center,such as type of the autonomous yard vehicle, current location of eachautonomous yard vehicle, work schedule of each autonomous yard vehicle.

The user account database 112 includes information associated with useraccounts, such as the user's profile, the user's previous deliveryhistory, etc.

Processing module 109 includes a seamless gate engine 113 and anassignment rules engine 114. The seamless gate engine 113 executes theprocesses, such as gate-in, gate-out, proof-of-delivery, etc., when theusers or drivers arrive at the distribution center. In one non-limitingexample, the assignment rules engine 114 assigns the autonomous vehiclesin the distribution center to the cargo trailers based on particularrules and load information received from the mobile application. Forexample, the assignment rules engine 114 can determine how to assign theautonomous tractors to the trailers based upon the received freightinformation, predetermined rules including locations of the autonomousvehicles and the trailer, priority of movement, freight requirements forthe assigned door, etc. In another non-limiting example, the assignmentrules engine 114 assigns, via the mobile application executing on themobile device of the driver, the driver a waiting area, dock or door towhich the load should be delivered based on particular rules and loadinformation received from the mobile application (e.g., freightinformation, priority of movement, freight requirements for the assigneddoor, etc.).

Communication interface 107, in accordance with various embodiments caninclude, but is not limited to, a radio frequency (RF) receiver, RFtransceiver, NFC device, a built-in network adapter, network interfacecard, PCMCIA network card, card bus network adapter, wireless networkadapter, USB network adapter, modem or any other device suitable forinterfacing with any type of network capable of communication andperforming the operations described herein. Processor 105, in accordancewith various embodiments can include, for example, but not limited to, amicrochip, a processor (e.g., a central processing unit, a graphicalprocessing unit), a microprocessor, a special purpose processor, anapplication specific integrated circuit, a microcontroller, a fieldprogrammable gate array, any other suitable processor, or combinationsthereof. The computing system 110 can also include, memory 104 such asbut not limited to, hardware memory, non-transitory tangible media,magnetic storage disks, optical disks, flash drives, computationaldevice memory, random access memory, such as but not limited to DRAM,SRAM, EDO RAM, any other type of memory, or combinations thereof.

The data storage device(s) 140 can hold load information database(s) 141containing load information related to each freight delivery. The loadinformation includes, for example, delivery number, purchase order (PO)number, progressive number (PRO) number, bill of lading (BOL) number,pickup date, freight information, etc.

User device 119 includes communication interface 121 for communicatingwith the computing system 110 and executes a mobile application 123.User device 119 may be smartphone, tablet or other mobile deviceequipped with a processor, communication interface 121 and a bundledmobile application 123 that includes a bundle having a main applicationand sub-applications, each of which are distinct and separateapplications having separate and distinct executable files. The bundledmobile application 123 can generate a user interface for accepting userinput and is configured to control an integrated data acquisition devicesuch as, but not limited to, an active short-range communication device,such as a NFC or RFID reader, to acquire NFC/RFID tag information, and,in an exemplary embodiment, a camera on a user device to capture imagesof items. For example, the mobile application 123 can acquire deliverynumber input by the users and generate a machine-readablerepresentation, such as a barcode, based on the load information relatedto the acquired delivery number.

FIG. 2 is a flow diagram illustrating a process for managing the loadsperformed by the load management system in a distribution centeraccording to an exemplary embodiment of the present disclosure. At step201, the user or driver logs in to a main application of the bundledmobile application using a mobile device. The user can log in to themain application using a federated login. The main application can beused to launch one or more of the sub-applications. Each of the mainapplication and the sub-applications can be separate and distinctexecutables that are executed as separate and distinct instances on themobile device. For example, the sub-applications can include distinctand independent applications for a gate-in process, a gate-out process,a proof-of-delivery (POD) process, as well as other processes.

In response to the user logging into the main application, thesub-applications can be accessed via the mobile device at step 203. Thesub-applications inherit credentials from the main application andcommunicate with each other in response to inheriting the credentials.When the main application is terminated, any of instances of thesub-applications that are being executed on the mobile device are alsoterminated accordingly. The main application and the sub-applicationsshare the load information and the pallet information related to theload, and share the user profile associated with the user account. Theload information can include driver information related to a driverdelivering the cargo trailer to the distribution center, a vehicletransporting the cargo trailer, a freight-type associated with each ofthe plurality of loads, estimated time of arrival, trailer number,Standard Carrier Alpha Code (SCAC), seal number, and freight type. Atstep 205, selectable icons corresponding to the sub-applications, suchas a first icon corresponding to gate-in sub-application, a second iconcorresponding to proof-of delivery sub-application, a third iconcorresponding to gate-out sub-application, etc., are rendered on adisplay of the mobile device and within a graphical user interface ofthe main application. At step 207, in response to the user selecting thefirst, second, or the third icon, the user's selection is received, andthe gate-in, proof-of delivery, or gate-out sub-application can belaunched or activated, respectively.

If the user selects the first icon at step 207, in case A, at step 209,the first sub-application, for example, a gate-in application, can belaunched or activated in response to the user's selection. The launchingor activation of the first sub-application results in execution of aninstance of the first sub-application by the mobile device in which theinstance inherits credentials and profile information from the instanceof the main application that is being executed. At step 211, the gate-inapplication acquires at least one of the identifications of the freightload. The identifications of the load include, for example, a deliverynumber, a load number, a purchase order (PO) number, and a bill oflading (BOL) number. The driver can enter the delivery number into thegate-in application by inputting the delivery number or taking a pictureof the delivery number that can be identified by the gate-inapplication.

At step 213, the gate-in application queries the database with theacquired identification of the loads, for the load information relatedto a specified load. At step 215 the gate-in application receives thequeried load information from the database, and then updates the loadinformation based on information of load documentation at step 217. Atstep 219 the gate-in application generates a machine-readablerepresentation corresponding to the identifications of the load, such asa barcode.

Then at point A, if the user terminates the gate-in sub-application, theprocess can go back to step 207 to launch or activate the othersub-applications in response to the user selecting other icons.Alternatively, without terminating the gate-in sub-application, the usercan launch or activate the proof-of-delivery or gate-out sub-applicationby selecting the corresponding icon, respectively.

If the user selects the second icon at step 207, in case B, at step 221,the second sub-application, for example, a proof-of-delivery (POD)application, can be launched or activated in response to the user'sselection. The launching or activation of the second sub-applicationresults in execution of an instance of the second sub-application by themobile device in which the instance inherits credentials and profileinformation from the instance of the main application that is beingexecuted and can inherit data or information from the instance of thefirst sub-application if the instance of the first sub-application isstill being executed (e.g., has not been terminated).

At step 223, the proof-of-delivery application acquires themachine-readable representation generated by the first sub-application,i.e., the gate-in application. At step 225, the proof-of-deliveryapplication queries the database with the acquired machine-readablerepresentation for the load information. Then at step 227 theproof-of-delivery application receives the queried load information fromthe database, and at step 229 pallet information of the load isacquired. At step 231, based on the acquired pallet information, theload information is updated in load information databases of the loadmanagement system.

At step 233 a computing system of the load management system receivesthe updated load information from the gate-in application and theproof-of-delivery application. At step 235 the updated load informationcan be transmitted to the database. At step 237 the computing system ofthe load management system receives an image of the machine-readablerepresentation scanned from the mobile device by the client device uponarrival of the cargo trailer at the gate. At step 239, the at least oneof the identifications of the load can be extracted from the scannedimage. Then at step 241, the computing system of the load managementsystem renders a map of the geographic area including a transferlocation at which the cargo trailer is to be dropped off after passingthrough the gate, and transmits the map and a load status to the mobiledevice associated with the user account at step 243, and the mobile appcan present a yard map. The load status can include a real-time statusof unloading freight indicating estimated time to complete unloading.

Then at point B, if the user terminates the proof-of-deliverysub-application, the process can go back to step 207 to launch oractivate the other sub-applications in response to the user selectingother icons. Alternatively, without terminating the proof-of-deliverysub-application, the user can launch or activate the gate-out or gate-insub-application by selecting the corresponding icon, respectively.

When the load tasks are completed, such as after the freight is loadedor unloaded, the gate-out process is needed before the user or driverleaves the distribution center. For example, the driver can pull thetrailer to the truck gate of the distribution center and stops for theasset protection (AP) associate verification. If the user selects thethird icon at step 207, in case C, at step 245, the thirdsub-application, for example the gate-out application, can be launchedor activated in response to the user's selection. The launching oractivation of the third sub-application results in execution of aninstance of the third sub-application by the mobile device in which theinstance inherits credentials and profile information from the instanceof the main application that is being executed and can inherit data orinformation from the instances of the first and/or secondsub-applications if the instances of the first and/or secondsub-applications are still being executed (e.g., has not beenterminated). At step 247, the gate-out application acquires themachine-readable representation generated by the first sub-application,i.e., the gate-in application. At step 249, the gate-out applicationqueries the database with the machine-readable representation for thepallet information and the load information related to the freight load.Then the gate-out application receives the pallet information and theload information from the database at step 251, and presents the palletinformation and the load information on the mobile device at step 253.

In one embodiment, the main mobile application provides security shellfor the sub-applications based on principles of inherency and thefederated login.

In another embodiment, the driver can obtain pallet information by usingthe mobile device to capture images of each pallet or scanning palletlabels, and the load management system can verify the pallet informationbased on the captured or scanned images of the pallets during thegate-in or gate-out process.

FIGS. 3A-3D are exemplary graphical user interfaces (GUIs) of a mobileapplication executed on a mobile device of the load management systemaccording to the present disclosure. As shown in FIGS. 3A-3B, after theuser or the driver launches the main mobile application, the user canlog in his/her account by entering username 311, password 313, businessunit 315, store number 317, and country 319. After logging in to themain application, as shown in FIG. 3C, the user can select thesub-application corresponding to the needed workflow, such as gate-inapplication 331, proof-of-delivery (POD) application 332, gate-outapplication 333, and good neighbor rewards (GNR) application 334.

FIG. 3D shows a GUI of the POD sub-application 332 indicating stopprogress. In FIG. 3D, timer 341 indicates the time elapsed for thecurrent load task. Stop progress 342 indicates that in the current task,there are three (3) unloaded pallets, one (1) pallet to reload, andtwelve (12) remaining pallets. A progress bar 343 shows the percentageof completion of the task using different colors. The user can tap theregion 344 to scan the machine-readable representation of each pallet,such as barcode, to acquire the related pallet information. When thepallet is damaged, the user can tap the region 345 to take photos of thedamaged pallets. The user can click the “FINISH” button 346 to submitthe uploaded barcode or photos.

FIGS. 4A-4D are exemplary graphical user interfaces (GUIs) of a gate-insub-application of the main application executed on the mobile device ofthe load management system according to the present disclosure. FIG. 4Ashows a GUI of acknowledgement of rules and regulations when the userselects gate-in process 331. By selecting the checkbox 411 and enteringthe user's name at name box 413, the user acknowledges and agrees to therules and regulations shown on the GUI screen in FIG. 4A. Therefore, theload management system transmits safety requirement to the mobile deviceand tracks safety review of the user associated with the mobile device.

Then as shown in FIG. 4B, the user can enter and submit delivery numberor load number 421 provided by the freight carrier. Alternatively, theuser can use the smartphone to photograph the delivery number or loadnumber from the paper bill of lading (BOL) provided by the freightcarrier. According to the delivery number submitted by the user, themobile app can acquire the load information related to the deliverynumber from databases provided by the freight carrier.

Then in the GUI shown in FIG. 4C, load information can be acquired fromthe database provided by the freight carrier. Alternatively, theadditional load information can be entered by the user. As shown in FIG.4C, the load information includes, for example, delivery number 431,distribution center (DC) number 432, purchase order (PO) count 433,carrier standard carrier alpha code (SCAC) 434, tractor number 435,trailer number 436, trailer type 437, and seal number 438. The user canclick the “Submit” button 439 to submit the load information. Then FIG.4D shows that the load information has been submitted. Then the user canclick the “Generate Barcode” button 441 to generate a barcode related tothe delivery number. The delivery details can be presented if the userclicks the “Delivery Details” button 442. If the user clicks the “Wheredo I park?” button 443, a map of the distribution center including alocation at which the user parks the truck can be presented on thescreen. The map can also provide a real-time location of the mobiledevice relative to the location using the mobile devices GPS receiver.

FIG. 5 is a block diagram of an exemplary computing device 510 such ascan be used, or portions thereof, in accordance with various embodimentsand, for clarity, refers back to and provides greater detail regardingvarious elements of the system 100 of FIG. 1. The computing device 510,which can be, but is not limited to the central computing system, theserver, user mobile device, POS device and data capture devicesdescribed herein, can include one or more non-transitorycomputer-readable media for storing one or more computer-executableinstructions or software for implementing exemplary embodiments. Thenon-transitory computer-readable media can include, but is not limitedto, one or more types of hardware memory, non-transitory tangible media(for example, one or more magnetic storage disks, one or more opticaldisks, one or more flash drives), and the like. For example, memory 104included in the computing device 510 can store computer-readable andcomputer-executable instructions or software for performing theoperations disclosed herein. For example, the memory 104 can store asoftware application 540 which is configured to perform the disclosedoperations (e.g., manage yard vehicles in a distribution center). Thecomputing device 510 can also include configurable and/or programmableprocessor 105 and an associated core 514, and optionally, one or moreadditional configurable and/or programmable processing devices, e.g.,processor(s) 512′ and associated core(s) 514′ (for example, in the caseof computational devices having multiple processors/cores), forexecuting computer-readable and computer-executable instructions orsoftware stored in the memory 104 and other programs for controllingsystem hardware. Processor 105 and processor(s) 512′ can each be asingle core processor or multiple core (514 and 514′) processor.

Virtualization can be employed in the computing device 510 so thatinfrastructure and resources in the computing device can be shareddynamically. A virtual machine 524 can be provided to handle a processrunning on multiple processors so that the process appears to be usingonly one computing resource rather than multiple computing resources.Multiple virtual machines can also be used with one processor.

Memory 104 can include a computational device memory or random accessmemory, such as DRAM, SRAM, EDO RAM, and the like. Memory 104 caninclude other types of memory as well, or combinations thereof.

A user can interact with the computing device 510 through a visualdisplay device 528, such as any suitable device capable of renderingtexts, graphics, and/or images including an LCD display, a plasmadisplay, projected image (e.g. from a Pico projector), Google Glass,Oculus Rift, HoloLens, and the like, and which can display one or moreuser interfaces 530 that can be provided in accordance with exemplaryembodiments. The computing device 510 can include other I/O devices forreceiving input from a user, for example, a keyboard or any suitablemulti-point touch (or gesture) interface 518, a pointing device 520(e.g., a mouse). The keyboard 518 and the pointing device 520 can becoupled to the visual display device 528. The computing device 510 caninclude other suitable conventional I/O peripherals.

The computing device 510 can also include one or more storage devices534, such as a hard-drive, CD-ROM, flash drive, or other computerreadable media, for storing data and computer-readable instructionsand/or software that perform operations disclosed herein. In someembodiments, the one or more storage devices 534 can be detachablycoupled to the computing device 510. Exemplary storage device 534 canalso store one or more software applications 540 for implementingprocesses of the load management system described herein and can includedatabases 542 for storing any suitable information required to implementexemplary embodiments. The databases can be updated manually orautomatically at any suitable time to add, delete, and/or update one ormore items in the databases. In some embodiments, at least one of thestorage device 534 can be remote from the computing device (e.g.,accessible through a communication network) and can be, for example,part of a cloud-based storage solution.

The computing device 510 can include a network interface 522 configuredto interface via one or more network devices 532 with one or morenetworks, for example, Local Area Network (LAN), Wide Area Network (WAN)or the Internet through a variety of connections including, but notlimited to, standard telephone lines, LAN or WAN links (for example,802.11, T1, T3, 56 kb, X.25), broadband connections (for example, ISDN,Frame Relay, ATM), wireless connections, controller area network (CAN),or some combination of any or all of the above. The network interface522 can include a built-in network adapter, network interface card,PCMCIA network card, card bus network adapter, wireless network adapter,USB network adapter, modem or any other device suitable for interfacingthe computing device 510 to any type of network capable of communicationand performing the operations described herein. Moreover, the computingdevice 510 can be any computational device, such as a workstation,desktop computer, server, laptop, handheld computer, tablet computer, orother form of computing or telecommunications device that is capable ofcommunication and that has sufficient processor power and memorycapacity to perform the operations described herein.

The computing device 510 can run operating systems 526, such as versionsof the Microsoft® Windows® operating systems, different releases of theUnix and Linux operating systems, versions of the MacOS® for Macintoshcomputers, embedded operating systems, real-time operating systems, opensource operating systems, proprietary operating systems, or otheroperating systems capable of running on the computing device andperforming the operations described herein. In exemplary embodiments,the operating system 526 can be run in native mode or emulated mode. Inan exemplary embodiment, the operating system 526 can be run on one ormore cloud machine instances.

FIG. 6 is a block diagram of exemplary distributed and/or cloud-basedembodiments. Although FIG. 1, and portions of the exemplary discussionabove, make reference to a load management system 100 operating on asingle computing device, one will recognize that various of the moduleswithin the load management system 100 may instead be distributed acrossa network 606 in separate server systems 601 a-d and/or in othercomputing devices, such as a desktop computer device 602, or mobilecomputer device 603. As another example, the user interface provided bythe mobile application 123 can be a client side application of aclient-server environment (e.g., a web browser or downloadableapplication, such as a mobile app), wherein the processing module 109 ishosted by one or more of the server systems 601 a-d (e.g., in acloud-based environment) and interacted with by the desktop computerdevice or mobile computer device. In some distributed systems, themodules of the system 100 can be separately located on server systems601 a-d and can be in communication with one another across the network606.

In describing exemplary embodiments, specific terminology is used forthe sake of clarity. For purposes of description, each specific term isintended to at least include all technical and functional equivalentsthat operate in a similar manner to accomplish a similar purpose.Additionally, in some instances where a particular exemplary embodimentincludes a multiple system elements, device components or method steps,those elements, components or steps may be replaced with a singleelement, component or step. Likewise, a single element, component orstep may be replaced with a multiple elements, components or steps thatserve the same purpose. Moreover, while exemplary embodiments have beenshown and described with references to particular embodiments thereof,those of ordinary skill in the art will understand that varioussubstitutions and alterations in form and detail may be made thereinwithout departing from the scope of the invention. Further still, otheraspects, functions and advantages are also within the scope of theinvention.

Exemplary flowcharts are provided herein for illustrative purposes andare non-limiting examples of methods. One of ordinary skill in the artwill recognize that exemplary methods may include more or fewer stepsthan those illustrated in the exemplary flowcharts, and that the stepsin the exemplary flowcharts may be performed in a different order thanthe order shown in the illustrative flowcharts.

The invention claimed is:
 1. A load management system for a distributioncenter, the system comprising: a database storing load informationrelated to a plurality of loads destined for the distribution center,the load information including an identification associated with eachload in the plurality of loads; a mobile application associated with auser account and executable on a mobile device, the mobile applicationincluding a main application and a plurality of independently executablesub-applications corresponding to workflow progresses in thedistribution center, the mobile device executes the mobile application,and the mobile application when executed: accesses, in response to auser logging in to the main mobile application associated with thecorresponding user account, the plurality of sub-applications, each ofthe main application and the plurality of sub-applications correspondingto separate and distinct executables and being executed as separate anddistinct instances; renders, on a display of the mobile device andwithin a graphical user interface of the main application, selectableicons corresponding to the plurality of sub-applications on the mobiledevice; activates a first sub-application of the plurality ofsub-applications in response to the user selecting a first one of theselectable icons corresponding to the first sub-application, the firstsub-application when executed: acquires at least one of a plurality ofidentifications of the loads; queries the database, with the acquired atleast one of the plurality of identifications of the loads, for the loadinformation related to a specified load; receives the queried loadinformation from the database; updates the load information based oninformation of load documentation; and generates a machine-readablerepresentation corresponding to the at least one of the plurality ofidentifications of the load; activates a second sub-application of theplurality of sub-applications in response to the user selecting a secondone of the selectable icons corresponding to the second sub-application,the second sub-application when executed: acquires the machine-readablerepresentation generated by the first sub-application; queries thedatabase, with the machine-readable representation, for the loadinformation related to the load; receives the queried load informationfrom the database; acquires pallet information; and updates the loadinformation based on the pallet information, wherein the plurality ofsub applications inherit credentials from the main application andcommunicate with each other in response to inheriting the credentials.2. The system of claim 1, further comprising: a computing system incommunication with the mobile device and the database, the computingsystem configured to: receive the updated load information from thefirst sub-application and the second sub-application; transmit theupdated load information to the database; receive, from a client deviceat a gate of the distribution center, an image of the machine-readablerepresentation scanned from the mobile device by the client device uponarrival of the cargo trailer at the gate; extract the at least one ofthe plurality of identifications of the load from the scanned image;render a map of the geographic area including a transfer location atwhich the cargo trailer is to be dropped off after passing through thegate; and transmit the map and a load status to the mobile deviceassociated with the user account.
 3. The system of claim 1, wherein themobile application when executed, further activates a thirdsub-application of the plurality of sub-applications in response to theuser selecting a third one of the selectable icons corresponding to thethird sub-application, the third sub-application when executed: acquiresthe machine-readable representation generated by the firstsub-application; queries the database, with the machine-readablerepresentation, for the pallet information and the load informationrelated to the load; receives the pallet information and the loadinformation from the database; and presents the pallet information andthe load information on the mobile device.
 4. The system of claim 1,wherein the mobile application and the plurality of sub-applicationsshare the load information and the pallet information related to theload and share user profile associated with the user account.
 5. Thesystem of claim 1, wherein the user logs in to the mobile applicationusing a federated login.
 6. The system of claim 5, wherein the mainmobile application provides security shell for the plurality ofsub-applications based on principles of inherency and the federatedlogin.
 7. The system of claim 1, wherein when the mobile application isterminated, the plurality of sub-applications are terminatedaccordingly.
 8. The system of claim 1, wherein each of the plurality ofidentifications of the loads include a delivery number, a load number, apurchase order (PO) number, and a bill of lading (BOL) number.
 9. Thesystem of claim 1, wherein the load information include driverinformation related to a driver delivering the cargo trailer to thedistribution center, a vehicle transporting the cargo trailer, afreight-type associated with each of the plurality of loads, estimatedtime of arrival, trailer number, Standard Carrier Alpha Code (SCAC),seal number, and freight type.
 10. The system of claim 1, wherein theload status includes a real-time status of unloading freight indicatingestimated time to complete unloading.
 11. The system of claim 1, whereinthe computing system further verifies pallet information based on imagesof each pallet of the load scanned by the mobile device.
 12. Acomputer-implemented method for remotely managing loads at adistribution center, comprising: accessing, in response to a userlogging in to a main mobile application included in a mobile applicationwhich is associated with a user account and executable on a mobiledevice, a plurality of sub-applications included in the mobileapplication, the plurality of sub-applications being independentlyexecutable and corresponding to workflow progresses in the distributioncenter, and each of the main application and the plurality ofsub-applications corresponding to separate and distinct executables andbeing executed as separate and distinct instances; rendering, on adisplay of the mobile device and within a graphical user interface ofthe main application, selectable icons corresponding to the plurality ofsub-applications on the mobile device; activating, by the mobileapplication, a first sub-application of the plurality ofsub-applications in response to the user selecting a first one of theselectable icons corresponding to the first sub-application, andexecuting the first sub-application, the process of executing the firstsub-application comprising: acquiring at least one of a plurality ofidentifications of the loads; querying a database, with the acquired atleast one of the plurality of identifications of the loads, for loadinformation related to a specified load, the database holding the loadinformation related to a plurality of loads stored in a cargo trailerdestined for the distribution center, and the load information includingan identification associated with each load in the plurality of loads;receiving the queried load information from the database; updating theload information based on information of load documentation; andgenerating a machine-readable representation corresponding to the atleast one of the plurality of identifications of the load; activating,by the mobile application, a second sub-application of the plurality ofsub-applications in response to the user selecting a second one of theselectable icons corresponding to the second sub-application, andexecuting the second sub-application, the process of executing thesecond sub-application comprising: acquiring the machine-readablerepresentation generated by the first sub-application; querying thedatabase, with the machine-readable representation, for the loadinformation related to the load; receiving the queried load informationfrom the database; acquiring pallet information; and updating the loadinformation based on the pallet information, wherein the plurality ofsub applications inherit credentials from the main application andcommunicate with each other in response to inheriting the credentials.13. The method of claim 12, further comprising receiving, by a computingsystem in communication with the mobile device and the database, theupdated load information from the first sub-application and the secondsub-application; transmitting, by the computing system, the updated loadinformation to the database; receiving, by the computing system, from aclient device at a gate of the distribution center, an image of themachine-readable representation scanned from the mobile device by theclient device upon arrival of the cargo trailer at the gate; extracting,by the computing system, the at least one of the plurality ofidentifications of the load from the scanned image; rendering, by thecomputing system, a map of the geographic area including a transferlocation at which the cargo trailer is to be dropped off after passingthrough the gate; and transmitting, by the computing system, the map anda load status to the mobile device associated with the user account. 14.The method of claim 12, further comprising activating a thirdsub-application of the plurality of sub-applications in response to theuser selecting a third one of the selectable icons corresponding to thethird sub-application, and executing the third sub-application, theprocess of executing the third sub-application comprising: acquiring themachine-readable representation generated by the first sub-application;querying the database, with the machine-readable representation, for thepallet information and the load information related to the load;receiving the pallet information and the load information from thedatabase; and presenting the pallet information and the load informationon the mobile device.
 15. The method of claim 12, further comprisingsharing, between the mobile application and the plurality ofsub-applications, the load information and the pallet informationrelated to the load, and user profile associated with the user account.16. The method of claim 12, further comprising logging in to the mobileapplication using a federated login.
 17. The method of claim 16, furthercomprising providing, by the main application, security shell for theplurality of sub-applications based on principles of inherency and thefederated login.
 18. The method of claim 12, further comprising when themobile application is terminated, terminating the plurality ofsub-applications accordingly.
 19. The method of claim 12, wherein eachof the plurality of identifications of the loads include a deliverynumber, a load number, a purchase order (PO) number, and a bill oflading (BOL) number.
 20. The method of claim 12, wherein the loadinformation include driver information related to a driver deliveringthe cargo trailer to the distribution center, a vehicle transporting thecargo trailer, a freight-type associated with each of the plurality ofloads, estimated time of arrival, trailer number, Standard Carrier AlphaCode (SCAC), seal number, and freight type.
 21. The method of claim 12,wherein the load status includes a real-time status of unloading freightindicating estimated time to complete unloading.
 22. The method of claim12, further comprising verifying, by the computing system, palletinformation based on images of each pallet of the load scanned by themobile device.